Conversation
There was a problem hiding this comment.
Pull request overview
This PR updates the GitHub Actions runner configuration for GPU-based CI jobs from gpumode-nvidia-arc to gpu-t4, likely to test a different runner infrastructure. The change also modifies the runner format from array to string.
- Changed runner name from
gpumode-nvidia-arctogpu-t4 - Modified runner format from array
[runner-name]to stringrunner-name
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
.github/workflows/runner_ci.yml
Outdated
| jobs: | ||
| check-cuda: | ||
| runs-on: [gpumode-nvidia-arc] | ||
| runs-on: gpu-t4 |
There was a problem hiding this comment.
The runner name format has changed from an array to a string. Other GPU-related workflows in this repository use array format for self-hosted runners (e.g., [nvidia-docker-b200-8-x86-64] in nvidia_workflow.yml and nvidia-arc-health.yml). While both formats are valid in GitHub Actions, using an array is the conventional format for self-hosted runners as it allows specifying multiple labels. Consider using [gpu-t4] instead of gpu-t4 for consistency with other workflows in the repository.
.github/workflows/runner_ci.yml
Outdated
|
|
||
| check-pytorch: | ||
| runs-on: [gpumode-nvidia-arc] | ||
| runs-on: gpu-t4 |
There was a problem hiding this comment.
The runner name format has changed from an array to a string. Other GPU-related workflows in this repository use array format for self-hosted runners (e.g., [nvidia-docker-b200-8-x86-64] in nvidia_workflow.yml and nvidia-arc-health.yml). While both formats are valid in GitHub Actions, using an array is the conventional format for self-hosted runners as it allows specifying multiple labels. Consider using [gpu-t4] instead of gpu-t4 for consistency with other workflows in the repository.
1 participant
Sad github doesn't provide free T4 gpus anymore